Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00a9a0eaee72a08105a5c3327daad92676cd01e49c35e0c1b61bc2d76109c4f2

Tx prefix hash: e8836c542d9ca41479179acc793c9697d0007c3fc61fa212749465e4bd7329f3
Tx public key: 7920e823f837f12b7a0db3aaeeaac462cee120640ed7e05e4e6e2c229b5bca49
Timestamp: 1703003315 Timestamp [UCT]: 2023-12-19 16:28:35 Age [y:d:h:m:s]: 01:334:10:38:46
Block: 916657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497874 RingCT/type: yes/0
Extra: 017920e823f837f12b7a0db3aaeeaac462cee120640ed7e05e4e6e2c229b5bca49021100000002e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d9a4b211d7459abc7c045429714c7e695ded2150b7e11bbffa936d801c2509b 0.600000000000 1374215 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": 916667, "vin": [ { "gen": { "height": 916657 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d9a4b211d7459abc7c045429714c7e695ded2150b7e11bbffa936d801c2509b" } } ], "extra": [ 1, 121, 32, 232, 35, 248, 55, 241, 43, 122, 13, 179, 170, 238, 170, 196, 98, 206, 225, 32, 100, 14, 215, 224, 94, 78, 110, 44, 34, 155, 91, 202, 73, 2, 17, 0, 0, 0, 2, 228, 187, 107, 131, 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