Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c28a86ae30245c700ea22daf2df0c320d715538effc3f0b99ce47468dcdb613

Tx prefix hash: 05f89c03ec36698a22e1622523b5dc9398a6816f40654055b2cfbd013fe7477c
Tx public key: cb42b4e4920f8960659cfd6e49086f6799c3b25ba16c9c4d8a3a57c02cc74549
Timestamp: 1709811027 Timestamp [UCT]: 2024-03-07 11:30:27 Age [y:d:h:m:s]: 01:265:10:30:32
Block: 973094 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 448447 RingCT/type: yes/0
Extra: 01cb42b4e4920f8960659cfd6e49086f6799c3b25ba16c9c4d8a3a57c02cc7454902110000000246812bb8000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94796a62c5cdc6098efec0f997d5a8fea0ec64fea7ceb43a6164971be5e33b2f 0.600000000000 1433025 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": 973104, "vin": [ { "gen": { "height": 973094 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94796a62c5cdc6098efec0f997d5a8fea0ec64fea7ceb43a6164971be5e33b2f" } } ], "extra": [ 1, 203, 66, 180, 228, 146, 15, 137, 96, 101, 156, 253, 110, 73, 8, 111, 103, 153, 195, 178, 91, 161, 108, 156, 77, 138, 58, 87, 192, 44, 199, 69, 73, 2, 17, 0, 0, 0, 2, 70, 129, 43, 184, 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