Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: f0e1c5839409ad9197eeca836f5dc567170bc2c6a7d938bbea1d1a70c16cf189

Tx prefix hash: 81b6f4f69252ac22fe73790c00fcdc70421ecbca9b16e74327f713af3fd2084e
Tx public key: 9dfce94b05a871ec9111fabfdad99a49c80a93d080bfb44efb528f82184a4c0f
Timestamp: 1719625086 Timestamp [UCT]: 2024-06-29 01:38:06 Age [y:d:h:m:s]: 00:281:11:39:16
Block: 1054440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201125 RingCT/type: yes/0
Extra: 019dfce94b05a871ec9111fabfdad99a49c80a93d080bfb44efb528f82184a4c0f0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b4b759d566b980cb13704dc5ec84682d6b85125a3bafb79505bf8ff5ee04cd3 0.600000000000 1524801 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1054450, "vin": [ { "gen": { "height": 1054440 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b4b759d566b980cb13704dc5ec84682d6b85125a3bafb79505bf8ff5ee04cd3" } } ], "extra": [ 1, 157, 252, 233, 75, 5, 168, 113, 236, 145, 17, 250, 191, 218, 217, 154, 73, 200, 10, 147, 208, 128, 191, 180, 78, 251, 82, 143, 130, 24, 74, 76, 15, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8