Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc064919109932ecfb3791d62856cf235c0e5dc47553594f57334d691c79a20b

Tx prefix hash: 7782fa3e44ca6f209cf66e3a7bd74edbc78fc6cd5a3aa5f461dd465fa99d7e10
Tx public key: 53348826a7820ef6bf176f1df9d8dd6028557b20c797f20a06e8544e4b57ad64
Timestamp: 1580408822 Timestamp [UCT]: 2020-01-30 18:27:02 Age [y:d:h:m:s]: 05:034:05:50:08
Block: 55611 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1175979 RingCT/type: yes/0
Extra: 0153348826a7820ef6bf176f1df9d8dd6028557b20c797f20a06e8544e4b57ad64021100000009d81c26c0000000000000000000

1 output(s) for total of 401.555891774000 dcy

stealth address amount amount idx
00: 8d366017a6ac7e805320bc6081b19e8ac4dba0828955f89ac462821f0dfcacac 401.555891774000 102623 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": 55621, "vin": [ { "gen": { "height": 55611 } } ], "vout": [ { "amount": 401555891774, "target": { "key": "8d366017a6ac7e805320bc6081b19e8ac4dba0828955f89ac462821f0dfcacac" } } ], "extra": [ 1, 83, 52, 136, 38, 167, 130, 14, 246, 191, 23, 111, 29, 249, 216, 221, 96, 40, 85, 123, 32, 199, 151, 242, 10, 6, 232, 84, 78, 75, 87, 173, 100, 2, 17, 0, 0, 0, 9, 216, 28, 38, 192, 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