Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0e3567ed4f05f26bcc45a539203ecf53c638c3a62cd09adffa5836d35ed37a1

Tx prefix hash: 802c105db71c3247d6e06c9977a5736b005c31fd42df5d631ffa1c354478b421
Tx public key: 8232264cbcb4add80dc177827d99ea7df904fbe1abd4431b12c2f23613a15167
Timestamp: 1719437605 Timestamp [UCT]: 2024-06-26 21:33:25 Age [y:d:h:m:s]: 01:135:00:40:33
Block: 1052878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355060 RingCT/type: yes/0
Extra: 018232264cbcb4add80dc177827d99ea7df904fbe1abd4431b12c2f23613a1516702110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba15a44a3dabe9c360640731e0c72a560751f47df183728c6d1ddd28a6f165c1 0.600000000000 1523215 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": 1052888, "vin": [ { "gen": { "height": 1052878 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba15a44a3dabe9c360640731e0c72a560751f47df183728c6d1ddd28a6f165c1" } } ], "extra": [ 1, 130, 50, 38, 76, 188, 180, 173, 216, 13, 193, 119, 130, 125, 153, 234, 125, 249, 4, 251, 225, 171, 212, 67, 27, 18, 194, 242, 54, 19, 161, 81, 103, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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