Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f214cc5ec97bbe516ca03b4ce48580785e1c6f5a59d3dcb9f6b48fd0d1aa98f

Tx prefix hash: c0bd1165c592264d49b1c596873e86c0cff0585e826858c77f31964e578517ff
Tx public key: 65fc227fd252a7d6b6397e010eb9e45ee246df329220814c872dbe2642ec60e3
Timestamp: 1584506282 Timestamp [UCT]: 2020-03-18 04:38:02 Age [y:d:h:m:s]: 04:328:10:47:22
Block: 84561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1130317 RingCT/type: yes/0
Extra: 0165fc227fd252a7d6b6397e010eb9e45ee246df329220814c872dbe2642ec60e3021100000005c2c2f844000000000000000000

1 output(s) for total of 321.969762565000 dcy

stealth address amount amount idx
00: 481dee8e9e753fe0cef35e1f8a63bde0e97027e7dc79dcbed28226a1b916a58c 321.969762565000 153235 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": 84571, "vin": [ { "gen": { "height": 84561 } } ], "vout": [ { "amount": 321969762565, "target": { "key": "481dee8e9e753fe0cef35e1f8a63bde0e97027e7dc79dcbed28226a1b916a58c" } } ], "extra": [ 1, 101, 252, 34, 127, 210, 82, 167, 214, 182, 57, 126, 1, 14, 185, 228, 94, 226, 70, 223, 50, 146, 32, 129, 76, 135, 45, 190, 38, 66, 236, 96, 227, 2, 17, 0, 0, 0, 5, 194, 194, 248, 68, 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