Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdb291af517c65a6fd8b3c634b24a88b0adc6027a14008a68d1fdbd248467bd0

Tx prefix hash: 5e07e39a1926d4451fca2c3bed4ba64c0e956a30605c23967cd0a0519ea2411e
Tx public key: ca93822dbb8e654b82a55996d7d01e4aa35969cfb385608fc2b61b3dfbf77b64
Timestamp: 1710203803 Timestamp [UCT]: 2024-03-12 00:36:43 Age [y:d:h:m:s]: 01:058:07:57:38
Block: 976353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302690 RingCT/type: yes/0
Extra: 01ca93822dbb8e654b82a55996d7d01e4aa35969cfb385608fc2b61b3dfbf77b640211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27098709f36d7043edc44d33b8e4142f7a4563c7a784baedf6ec41293b6c27ae 0.600000000000 1436346 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": 976363, "vin": [ { "gen": { "height": 976353 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27098709f36d7043edc44d33b8e4142f7a4563c7a784baedf6ec41293b6c27ae" } } ], "extra": [ 1, 202, 147, 130, 45, 187, 142, 101, 75, 130, 165, 89, 150, 215, 208, 30, 74, 163, 89, 105, 207, 179, 133, 96, 143, 194, 182, 27, 61, 251, 247, 123, 100, 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