Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f240e815cdc49012b8e3c426cfd265101636ae2d525c160842c76ff9afd82325

Tx prefix hash: a9ab319747e85aaa30d0443202b2a5f6a6c79fe26339a444e2018a9ed6655e5b
Tx public key: 9dc15d71778f5f2df268022ca2d3fd6406783332c4f3caa73612efe421a164dc
Timestamp: 1711315011 Timestamp [UCT]: 2024-03-24 21:16:51 Age [y:d:h:m:s]: 00:181:01:18:41
Block: 985575 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129672 RingCT/type: yes/0
Extra: 019dc15d71778f5f2df268022ca2d3fd6406783332c4f3caa73612efe421a164dc0211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac5f1c78c34323ded2b9264805b913bab8c1c1064aa424cd7c12bfcc2f899f1a 0.600000000000 1445792 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": 985585, "vin": [ { "gen": { "height": 985575 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac5f1c78c34323ded2b9264805b913bab8c1c1064aa424cd7c12bfcc2f899f1a" } } ], "extra": [ 1, 157, 193, 93, 113, 119, 143, 95, 45, 242, 104, 2, 44, 162, 211, 253, 100, 6, 120, 51, 50, 196, 243, 202, 167, 54, 18, 239, 228, 33, 161, 100, 220, 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