Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dac02d22282408fe79d6b186cbab3d50c7564457adf2458ac67345bcd92a9e2f

Tx prefix hash: abe88349156927bdd7a370e125242def86caa1c223b1026fb4539f9540173530
Tx public key: 6fb1eea7c58e934d20181611643342615d7da1c4dd2bf2b793ef953e97acddab
Timestamp: 1696041867 Timestamp [UCT]: 2023-09-30 02:44:27 Age [y:d:h:m:s]: 01:048:03:10:15
Block: 859129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295637 RingCT/type: yes/0
Extra: 016fb1eea7c58e934d20181611643342615d7da1c4dd2bf2b793ef953e97acddab0211000000034b8f5122000000000000000000

1 output(s) for total of 0.873673222000 dcy

stealth address amount amount idx
00: 3f0bd2b2b7070f7a7fe4b73f140c67ba014b21c7fb7a6f29fe86b688827a5957 0.873673222000 1313339 of 0

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": 859139, "vin": [ { "gen": { "height": 859129 } } ], "vout": [ { "amount": 873673222, "target": { "key": "3f0bd2b2b7070f7a7fe4b73f140c67ba014b21c7fb7a6f29fe86b688827a5957" } } ], "extra": [ 1, 111, 177, 238, 167, 197, 142, 147, 77, 32, 24, 22, 17, 100, 51, 66, 97, 93, 125, 161, 196, 221, 43, 242, 183, 147, 239, 149, 62, 151, 172, 221, 171, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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