Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2a76f4719f838c953a69accb1bf0ee1ab98665d8ad03a2033b2f087658552ce

Tx prefix hash: 12d34ae1e400eea4fe63fa5c30565c760d25ea1cc17b8f39bd8f3332422c86a9
Tx public key: d1cc00077639fbb9b0337d82e8aea383640cbb75f1750473751ef078b319d9cb
Timestamp: 1729652267 Timestamp [UCT]: 2024-10-23 02:57:47 Age [y:d:h:m:s]: 00:032:04:28:21
Block: 1137550 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22985 RingCT/type: yes/0
Extra: 01d1cc00077639fbb9b0337d82e8aea383640cbb75f1750473751ef078b319d9cb021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33186e9dcd0e9c47a1f610e3648288af03a22e587e38c1e39ca6d01ad4f8a58c 0.600000000000 1621061 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": 1137560, "vin": [ { "gen": { "height": 1137550 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33186e9dcd0e9c47a1f610e3648288af03a22e587e38c1e39ca6d01ad4f8a58c" } } ], "extra": [ 1, 209, 204, 0, 7, 118, 57, 251, 185, 176, 51, 125, 130, 232, 174, 163, 131, 100, 12, 187, 117, 241, 117, 4, 115, 117, 30, 240, 120, 179, 25, 217, 203, 2, 17, 0, 0, 0, 8, 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