Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11b7cfc5256ac4c1004c051e25467efd76b6866603332a2dc0271f79fa4fad23

Tx prefix hash: e438f73be2c3a809ab2c71b7635aa147c3296f41cf2cb0475e6f279aacc62fa9
Tx public key: 716ac0d0f75470f5a7d25eb6ab242de0dd8666ed24622dd4e32ea6361750b06c
Timestamp: 1737195564 Timestamp [UCT]: 2025-01-18 10:19:24 Age [y:d:h:m:s]: 00:151:03:56:55
Block: 1199967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107729 RingCT/type: yes/0
Extra: 01716ac0d0f75470f5a7d25eb6ab242de0dd8666ed24622dd4e32ea6361750b06c0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9945aece99f8ec834b0a627a7034e8c796a7cc9bc2bb8380c84d78a6e3e04da8 0.600000000000 1686608 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": 1199977, "vin": [ { "gen": { "height": 1199967 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9945aece99f8ec834b0a627a7034e8c796a7cc9bc2bb8380c84d78a6e3e04da8" } } ], "extra": [ 1, 113, 106, 192, 208, 247, 84, 112, 245, 167, 210, 94, 182, 171, 36, 45, 224, 221, 134, 102, 237, 36, 98, 45, 212, 227, 46, 166, 54, 23, 80, 176, 108, 2, 17, 0, 0, 0, 4, 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