Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eba029b2be7a2dae3176a8017cbdce46184d615fb48846ec946cc03ce39ae504

Tx prefix hash: 83b282f389f64fc9234087461998c9b7fb6a8e859ac3765e3b6796788fb6f529
Tx public key: 4a0a8b1b42f169b8efbd6585132590b16b3f9c40cd364e8cf13fb257c04f8467
Timestamp: 1711309960 Timestamp [UCT]: 2024-03-24 19:52:40 Age [y:d:h:m:s]: 01:056:20:40:39
Block: 985526 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301625 RingCT/type: yes/0
Extra: 014a0a8b1b42f169b8efbd6585132590b16b3f9c40cd364e8cf13fb257c04f84670211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ea474687a9f5769dfeafedfc64671b940a16fa8ad09c854e899ca797baf79be 0.600000000000 1445739 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": 985536, "vin": [ { "gen": { "height": 985526 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ea474687a9f5769dfeafedfc64671b940a16fa8ad09c854e899ca797baf79be" } } ], "extra": [ 1, 74, 10, 139, 27, 66, 241, 105, 184, 239, 189, 101, 133, 19, 37, 144, 177, 107, 63, 156, 64, 205, 54, 78, 140, 241, 63, 178, 87, 192, 79, 132, 103, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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