Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fbd2dae4d95ada3d0d294c1ec5baf4e0c1a47366c6c100d77c2d529b1302ef60

Tx prefix hash: e74370a9bfcf3a2a4bb42ec859b7b9c78e6aa81ee073a1b04da77378b0016c23
Tx public key: e53aa0df25682b22590d288c823d72df12a2a736adf79a18fc72ea108f076c20
Timestamp: 1715068337 Timestamp [UCT]: 2024-05-07 07:52:17 Age [y:d:h:m:s]: 00:338:06:45:20
Block: 1016676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241805 RingCT/type: yes/0
Extra: 01e53aa0df25682b22590d288c823d72df12a2a736adf79a18fc72ea108f076c2002110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd1d6fd562f7b74b9b761ff58b730acc4bf3a1e93c324a7c1cbc35ad7a3ed4ed 0.600000000000 1480329 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": 1016686, "vin": [ { "gen": { "height": 1016676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd1d6fd562f7b74b9b761ff58b730acc4bf3a1e93c324a7c1cbc35ad7a3ed4ed" } } ], "extra": [ 1, 229, 58, 160, 223, 37, 104, 43, 34, 89, 13, 40, 140, 130, 61, 114, 223, 18, 162, 167, 54, 173, 247, 154, 24, 252, 114, 234, 16, 143, 7, 108, 32, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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