Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71194075d9de8ad5b14e344c271609bc30cb8d444c020281b1c4df6b59ad3a18

Tx prefix hash: 519c8d34c75da035bf74e81ddd05e4ea1cb2624870672f8b70fba4020a690764
Tx public key: bf6ea64970c6264fcb32281e0629fb83f5f47dbcba15a714ffa7fef117ac37dd
Timestamp: 1712995011 Timestamp [UCT]: 2024-04-13 07:56:51 Age [y:d:h:m:s]: 01:200:23:46:30
Block: 999463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 402324 RingCT/type: yes/0
Extra: 01bf6ea64970c6264fcb32281e0629fb83f5f47dbcba15a714ffa7fef117ac37dd0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bcdc9766c29af9cfbf8af0ce57a36f58bd3e59fc2b08971b1cf5c4bb043a8d6b 0.600000000000 1459943 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": 999473, "vin": [ { "gen": { "height": 999463 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcdc9766c29af9cfbf8af0ce57a36f58bd3e59fc2b08971b1cf5c4bb043a8d6b" } } ], "extra": [ 1, 191, 110, 166, 73, 112, 198, 38, 79, 203, 50, 40, 30, 6, 41, 251, 131, 245, 244, 125, 188, 186, 21, 167, 20, 255, 167, 254, 241, 23, 172, 55, 221, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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