Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a9728a84f3530d0ad56273168f100dcb8a907f5f896a047bd5b3f37ceff3eeb

Tx prefix hash: 23de661d08fb065df167815f837b0c37aadc52694dc7cd0a73be2ec2b22eae07
Tx public key: 763e3015428d38ffec024f453ea9e6e843817e45edb8804dd3782c3e1fa3c7d7
Timestamp: 1644662712 Timestamp [UCT]: 2022-02-12 10:45:12 Age [y:d:h:m:s]: 02:314:14:49:34
Block: 436955 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 744189 RingCT/type: yes/0
Extra: 01763e3015428d38ffec024f453ea9e6e843817e45edb8804dd3782c3e1fa3c7d7021100000001a272b9cb000000000000000000

1 output(s) for total of 21.887038116000 dcy

stealth address amount amount idx
00: e1eb1a2d01f179ba3f3370f77bc28c58e4be07ed14d8ae32f6894e9ed90b1123 21.887038116000 848442 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": 436965, "vin": [ { "gen": { "height": 436955 } } ], "vout": [ { "amount": 21887038116, "target": { "key": "e1eb1a2d01f179ba3f3370f77bc28c58e4be07ed14d8ae32f6894e9ed90b1123" } } ], "extra": [ 1, 118, 62, 48, 21, 66, 141, 56, 255, 236, 2, 79, 69, 62, 169, 230, 232, 67, 129, 126, 69, 237, 184, 128, 77, 211, 120, 44, 62, 31, 163, 199, 215, 2, 17, 0, 0, 0, 1, 162, 114, 185, 203, 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