Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 462279cf3c80385fd30c3635b2b4cca854b224bff42bb1789cec0ae1ff1827ef

Tx prefix hash: 95e45ef1e71833c4100bc5aa4547da8bead44df83e5ace479a8d49ff1a023422
Tx public key: f22e82d78898238dee2f4f9941135d15a041ba0929937ce2816693dcf0d09db0
Timestamp: 1580702866 Timestamp [UCT]: 2020-02-03 04:07:46 Age [y:d:h:m:s]: 05:274:19:34:02
Block: 57707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1345975 RingCT/type: yes/0
Extra: 01f22e82d78898238dee2f4f9941135d15a041ba0929937ce2816693dcf0d09db0021100000002dcee4b4d000000000000000000

1 output(s) for total of 395.178742909000 dcy

stealth address amount amount idx
00: e287e0901fddd2a8830f79c8d268936857f5f63c3808b8addfcb21f9450a28e2 395.178742909000 106649 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": 57717, "vin": [ { "gen": { "height": 57707 } } ], "vout": [ { "amount": 395178742909, "target": { "key": "e287e0901fddd2a8830f79c8d268936857f5f63c3808b8addfcb21f9450a28e2" } } ], "extra": [ 1, 242, 46, 130, 215, 136, 152, 35, 141, 238, 47, 79, 153, 65, 19, 93, 21, 160, 65, 186, 9, 41, 147, 124, 226, 129, 102, 147, 220, 240, 208, 157, 176, 2, 17, 0, 0, 0, 2, 220, 238, 75, 77, 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