Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43e96df210cb8a9308ce20465f3f5d4ade2eeffadf93a68e12e8a42d79a05f62

Tx prefix hash: 243e61e5cf92aa07ef3b6d8d7e152b5dee79eb64c5c27694d83cab0e23c83c76
Tx public key: b6520d4e1c1ea3d3f176cd4a72da65202553fb044338a8b87cf1adb495468d20
Timestamp: 1711363414 Timestamp [UCT]: 2024-03-25 10:43:34 Age [y:d:h:m:s]: 00:337:01:17:20
Block: 985978 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240938 RingCT/type: yes/0
Extra: 01b6520d4e1c1ea3d3f176cd4a72da65202553fb044338a8b87cf1adb495468d2002110000000179bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52f0e68c3497e56e124ea03d4ebb00fbf3068981ae1943061f96ba8818e6b528 0.600000000000 1446199 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": 985988, "vin": [ { "gen": { "height": 985978 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52f0e68c3497e56e124ea03d4ebb00fbf3068981ae1943061f96ba8818e6b528" } } ], "extra": [ 1, 182, 82, 13, 78, 28, 30, 163, 211, 241, 118, 205, 74, 114, 218, 101, 32, 37, 83, 251, 4, 67, 56, 168, 184, 124, 241, 173, 180, 149, 70, 141, 32, 2, 17, 0, 0, 0, 1, 121, 189, 163, 190, 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