Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b3e11c48e262fb160549fb9e70e5d9b7e5525145a764186056de0bc5b58557c

Tx prefix hash: fc5cece536cf70abbf8bc554606ffa886833180d4dcffeb23074521affe68490
Tx public key: d537f7a9d27e467928c2d42c6679d1ff1b4e703de576d0453d99b2568d79d449
Timestamp: 1736168572 Timestamp [UCT]: 2025-01-06 13:02:52 Age [y:d:h:m:s]: 00:099:05:38:04
Block: 1191478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70696 RingCT/type: yes/0
Extra: 01d537f7a9d27e467928c2d42c6679d1ff1b4e703de576d0453d99b2568d79d449021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d3ba6e6899f3f10edd33c0bc852ebd9d0ca0a812c6d47c40e880c91d662f796 0.600000000000 1678017 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": 1191488, "vin": [ { "gen": { "height": 1191478 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d3ba6e6899f3f10edd33c0bc852ebd9d0ca0a812c6d47c40e880c91d662f796" } } ], "extra": [ 1, 213, 55, 247, 169, 210, 126, 70, 121, 40, 194, 212, 44, 102, 121, 209, 255, 27, 78, 112, 61, 229, 118, 208, 69, 61, 153, 178, 86, 141, 121, 212, 73, 2, 17, 0, 0, 0, 1, 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