Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d787d7cb10c7f2b3681f77fe67f5d09496668409d9b74c5539a1e64557dac60a

Tx prefix hash: 72a89219ec4f2d352861d7ce53b0c715a9db5bdc427fc3b996605d34298fe86a
Tx public key: 3700d0f37ca1894dc4e35e50e95eefe562d5642c2cf78bf9aa912c13747384ca
Timestamp: 1681779979 Timestamp [UCT]: 2023-04-18 01:06:19 Age [y:d:h:m:s]: 01:184:12:15:12
Block: 740934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393379 RingCT/type: yes/0
Extra: 013700d0f37ca1894dc4e35e50e95eefe562d5642c2cf78bf9aa912c13747384ca0211000000075029cbac000000000000000000

1 output(s) for total of 2.152674162000 dcy

stealth address amount amount idx
00: 516764a091d1ee9b39d651cbb28792aa2bbf54d6fe9b839d8382a3568dc7c170 2.152674162000 1187843 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": 740944, "vin": [ { "gen": { "height": 740934 } } ], "vout": [ { "amount": 2152674162, "target": { "key": "516764a091d1ee9b39d651cbb28792aa2bbf54d6fe9b839d8382a3568dc7c170" } } ], "extra": [ 1, 55, 0, 208, 243, 124, 161, 137, 77, 196, 227, 94, 80, 233, 94, 239, 229, 98, 213, 100, 44, 44, 247, 139, 249, 170, 145, 44, 19, 116, 115, 132, 202, 2, 17, 0, 0, 0, 7, 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