Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b7bbda065b9f5adcfec328328ad86e0f9ba2ba6a610cbbdeb06ebddc08d1541

Tx prefix hash: 016699caf11277a95dd6eb7cdb7b4d4b4736aa422e71c9db2a87a7a42155f90f
Tx public key: 337d4d001ffbcac2a7a333e3f6cbc3297e38b14648ad8c78ad4b324d379d74f3
Timestamp: 1715007752 Timestamp [UCT]: 2024-05-06 15:02:32 Age [y:d:h:m:s]: 00:357:22:54:26
Block: 1016169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255895 RingCT/type: yes/0
Extra: 01337d4d001ffbcac2a7a333e3f6cbc3297e38b14648ad8c78ad4b324d379d74f30211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8041d8bdcfe86fece7bdb91dec92dad029ca5171e83015e51ea17056f3714db3 0.600000000000 1479676 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": 1016179, "vin": [ { "gen": { "height": 1016169 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8041d8bdcfe86fece7bdb91dec92dad029ca5171e83015e51ea17056f3714db3" } } ], "extra": [ 1, 51, 125, 77, 0, 31, 251, 202, 194, 167, 163, 51, 227, 246, 203, 195, 41, 126, 56, 177, 70, 72, 173, 140, 120, 173, 75, 50, 77, 55, 157, 116, 243, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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