Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0bfe91b48332529f6ee5d935dbc0eff56b7a35bcc30fab1952530a5f06bd992

Tx prefix hash: 1b4b6e95d2598d7836ed650d6fa1405150c6a64cb7a96d26917c2faeca2eae98
Tx public key: ae740fc415aabb0960e5b6fcd176a3e91dd897ec4c7cfa72d67c25c5f2521bdd
Timestamp: 1695922413 Timestamp [UCT]: 2023-09-28 17:33:33 Age [y:d:h:m:s]: 01:049:14:53:30
Block: 858140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296702 RingCT/type: yes/0
Extra: 01ae740fc415aabb0960e5b6fcd176a3e91dd897ec4c7cfa72d67c25c5f2521bdd0211000000061c703914000000000000000000

1 output(s) for total of 0.880290457000 dcy

stealth address amount amount idx
00: 271fc5e43aa03aa1edea7a1f828f0a6b035d517db91460393b82cd7bf5aa353e 0.880290457000 1312304 of 0

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": 858150, "vin": [ { "gen": { "height": 858140 } } ], "vout": [ { "amount": 880290457, "target": { "key": "271fc5e43aa03aa1edea7a1f828f0a6b035d517db91460393b82cd7bf5aa353e" } } ], "extra": [ 1, 174, 116, 15, 196, 21, 170, 187, 9, 96, 229, 182, 252, 209, 118, 163, 233, 29, 216, 151, 236, 76, 124, 250, 114, 214, 124, 37, 197, 242, 82, 27, 221, 2, 17, 0, 0, 0, 6, 28, 112, 57, 20, 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