Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fb70d0e2435f915614a73dde7360a1406cb9bc03aa84dd4beeae7c975f426fa

Tx prefix hash: e5e2fdcd0cdd9894fba7d3ec66616bbd8d110dd29384f39dcb192a66cbb59c1a
Tx public key: 332ca1c4655bd18027993d6ba4f820f79a66dd410df2321b5eb75d573b5244de
Timestamp: 1737475649 Timestamp [UCT]: 2025-01-21 16:07:29 Age [y:d:h:m:s]: 00:052:07:16:11
Block: 1202241 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37203 RingCT/type: yes/0
Extra: 01332ca1c4655bd18027993d6ba4f820f79a66dd410df2321b5eb75d573b5244de021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a99db4b47cb6b0900c8dcc5cbca4596d17e5eb140b01e90bae52d4d07937bebb 0.600000000000 1688904 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": 1202251, "vin": [ { "gen": { "height": 1202241 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a99db4b47cb6b0900c8dcc5cbca4596d17e5eb140b01e90bae52d4d07937bebb" } } ], "extra": [ 1, 51, 44, 161, 196, 101, 91, 209, 128, 39, 153, 61, 107, 164, 248, 32, 247, 154, 102, 221, 65, 13, 242, 50, 27, 94, 183, 93, 87, 59, 82, 68, 222, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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