Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b978352f6f0e2a147e1ecf53ad57669cd5298bbe1b0de8deeb1da9a37ab26be

Tx prefix hash: bec0f5bbb05fb6fc347e85f4d18f2b7c7ba887f54021642c3771c41e8b14fa5b
Tx public key: f480c05d87ef39441668734e60e8a9c50b8cd9e0aa096cc08e84548178d59bf3
Timestamp: 1669060088 Timestamp [UCT]: 2022-11-21 19:48:08 Age [y:d:h:m:s]: 02:097:11:05:00
Block: 636156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 591316 RingCT/type: yes/0
Extra: 01f480c05d87ef39441668734e60e8a9c50b8cd9e0aa096cc08e84548178d59bf30211000000025029cbac000000000000000000

1 output(s) for total of 4.787966443000 dcy

stealth address amount amount idx
00: 95bce12036279cb650d5a6d9b0c256c4ff7b35217c218e1575d48c7bad9b1018 4.787966443000 1075547 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": 636166, "vin": [ { "gen": { "height": 636156 } } ], "vout": [ { "amount": 4787966443, "target": { "key": "95bce12036279cb650d5a6d9b0c256c4ff7b35217c218e1575d48c7bad9b1018" } } ], "extra": [ 1, 244, 128, 192, 93, 135, 239, 57, 68, 22, 104, 115, 78, 96, 232, 169, 197, 11, 140, 217, 224, 170, 9, 108, 192, 142, 132, 84, 129, 120, 213, 155, 243, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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