Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52d0379dd4f41f1b87e54d284d9edb74394c5ce40af36396f185a0e604cc5367

Tx prefix hash: aa149112f206bdebee196bb19e0ce313f8e658d3b05aadbdff851d3f680170c3
Tx public key: c1b4bfba3375ffc85ae8cdb160032d74befa3b353a8aa715f51f36eaddc23a7d
Timestamp: 1713972274 Timestamp [UCT]: 2024-04-24 15:24:34 Age [y:d:h:m:s]: 00:306:08:08:00
Block: 1007578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218968 RingCT/type: yes/0
Extra: 01c1b4bfba3375ffc85ae8cdb160032d74befa3b353a8aa715f51f36eaddc23a7d02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8efbbe8e26e456a860f035fdd004559866ca24422d9de8f447e8ea37e142d446 0.600000000000 1468966 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": 1007588, "vin": [ { "gen": { "height": 1007578 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8efbbe8e26e456a860f035fdd004559866ca24422d9de8f447e8ea37e142d446" } } ], "extra": [ 1, 193, 180, 191, 186, 51, 117, 255, 200, 90, 232, 205, 177, 96, 3, 45, 116, 190, 250, 59, 53, 58, 138, 167, 21, 245, 31, 54, 234, 221, 194, 58, 125, 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