Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c500b232d1973f317132b8ac014e02aaabd2d84d0f95d0471fcd9d9d072c05b

Tx prefix hash: 194daa3d3dd67aa2c8bbb96092af3a4a5fd80617189d0d4711cf638f2f7b4533
Tx public key: aaf0d1183b6dc0c1e5e941dc40fd15822b6e83e5cbec9faa0145b6382613288e
Timestamp: 1669425324 Timestamp [UCT]: 2022-11-26 01:15:24 Age [y:d:h:m:s]: 02:134:01:31:09
Block: 639167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 617517 RingCT/type: yes/0
Extra: 01aaf0d1183b6dc0c1e5e941dc40fd15822b6e83e5cbec9faa0145b6382613288e0211000000025029cbac000000000000000000

1 output(s) for total of 4.679230084000 dcy

stealth address amount amount idx
00: 799b1f008aa4e5c3b99153d570d8e2e2381c0e6ff0eea7fadaadce5b01a84c58 4.679230084000 1078806 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": 639177, "vin": [ { "gen": { "height": 639167 } } ], "vout": [ { "amount": 4679230084, "target": { "key": "799b1f008aa4e5c3b99153d570d8e2e2381c0e6ff0eea7fadaadce5b01a84c58" } } ], "extra": [ 1, 170, 240, 209, 24, 59, 109, 192, 193, 229, 233, 65, 220, 64, 253, 21, 130, 43, 110, 131, 229, 203, 236, 159, 170, 1, 69, 182, 56, 38, 19, 40, 142, 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