Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f57e5f543a090ea8497eb07907a3adfe2d770bf3a7e394de0738011135187de

Tx prefix hash: aef40da136f5e8b32b4dacbf13bdb4b52d8b6a8f73eb63297fa587feb0891436
Tx public key: 659f71d3ba53e8df8d7710a2134804e88b50d9a9ff372b7575f25ea83dc2f030
Timestamp: 1704702548 Timestamp [UCT]: 2024-01-08 08:29:08 Age [y:d:h:m:s]: 01:078:00:38:49
Block: 930720 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316856 RingCT/type: yes/0
Extra: 01659f71d3ba53e8df8d7710a2134804e88b50d9a9ff372b7575f25ea83dc2f0300211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c3fb67a04edaa11cab40ad869079ca53bf8a4c96a1f93d01fed128d1a984f22 0.600000000000 1388608 of 15

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": 930730, "vin": [ { "gen": { "height": 930720 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c3fb67a04edaa11cab40ad869079ca53bf8a4c96a1f93d01fed128d1a984f22" } } ], "extra": [ 1, 101, 159, 113, 211, 186, 83, 232, 223, 141, 119, 16, 162, 19, 72, 4, 232, 139, 80, 217, 169, 255, 55, 43, 117, 117, 242, 94, 168, 61, 194, 240, 48, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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