Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dff489f3078e60871b8c45c3020acf513f7c8c7031398a8cb5b59c6659d64dbd

Tx prefix hash: de6808130dd3e297151351c570531cce576ab6efcaacec0c34673b0e5b931c3a
Tx public key: 0573651f8b84d064c0fe79ca636238a6ad2620f6a08d83a564a5b560f42dc1b5
Timestamp: 1721062105 Timestamp [UCT]: 2024-07-15 16:48:25 Age [y:d:h:m:s]: 00:225:02:43:12
Block: 1066375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160775 RingCT/type: yes/0
Extra: 010573651f8b84d064c0fe79ca636238a6ad2620f6a08d83a564a5b560f42dc1b502110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f7c0245b9318be1dd3980b262e8323211d6859bee9c8c42bf585083474e24d0 0.600000000000 1536948 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": 1066385, "vin": [ { "gen": { "height": 1066375 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f7c0245b9318be1dd3980b262e8323211d6859bee9c8c42bf585083474e24d0" } } ], "extra": [ 1, 5, 115, 101, 31, 139, 132, 208, 100, 192, 254, 121, 202, 99, 98, 56, 166, 173, 38, 32, 246, 160, 141, 131, 165, 100, 165, 181, 96, 244, 45, 193, 181, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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