Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db0de90ac0a2c3374e6fe3a2be7a79d92c8b4cc4c7984b543c6ae0cea6df63bd

Tx prefix hash: b07808a8aeb40186aab0041ea8412fd0dbd4f6ef41fe42d2ed562467539a76d0
Tx public key: a224dc1deddf883f6e00726fb2765e16f6920c1a430061f4298974ae6dd850aa
Timestamp: 1713247669 Timestamp [UCT]: 2024-04-16 06:07:49 Age [y:d:h:m:s]: 01:062:17:41:21
Block: 1001558 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305713 RingCT/type: yes/0
Extra: 01a224dc1deddf883f6e00726fb2765e16f6920c1a430061f4298974ae6dd850aa02110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 394073423188f2b557c3682402447a68097b4dff0505c8f5b077ff3820cbd746 0.600000000000 1462064 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": 1001568, "vin": [ { "gen": { "height": 1001558 } } ], "vout": [ { "amount": 600000000, "target": { "key": "394073423188f2b557c3682402447a68097b4dff0505c8f5b077ff3820cbd746" } } ], "extra": [ 1, 162, 36, 220, 29, 237, 223, 136, 63, 110, 0, 114, 111, 178, 118, 94, 22, 246, 146, 12, 26, 67, 0, 97, 244, 41, 137, 116, 174, 109, 216, 80, 170, 2, 17, 0, 0, 0, 8, 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