Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11db1fe31cf9c85d3d1057f29f44f43253331182cc26ff0bbbf938b0f197d03f

Tx prefix hash: ba36fe63b08bfde93a637445aef5a16f73d9d73eb52fb74b59a49c5d4b03d6a2
Tx public key: 0907902c2ba9e0cd3c44785b629e4d3a100b009ad33ffacbd5720dcd42efcb79
Timestamp: 1737062916 Timestamp [UCT]: 2025-01-16 21:28:36 Age [y:d:h:m:s]: 00:153:01:59:49
Block: 1198857 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109114 RingCT/type: yes/0
Extra: 010907902c2ba9e0cd3c44785b629e4d3a100b009ad33ffacbd5720dcd42efcb790211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a964695752b5df8cd39114bce436c3d1e7d89c37f97aedaaf9e7056322ae8e51 0.600000000000 1685484 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": 1198867, "vin": [ { "gen": { "height": 1198857 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a964695752b5df8cd39114bce436c3d1e7d89c37f97aedaaf9e7056322ae8e51" } } ], "extra": [ 1, 9, 7, 144, 44, 43, 169, 224, 205, 60, 68, 120, 91, 98, 158, 77, 58, 16, 11, 0, 154, 211, 63, 250, 203, 213, 114, 13, 205, 66, 239, 203, 121, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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