Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cdc6c4177e8a7457f307b48fdedf5047d1da5cfadf32f5eb17506b15fa8820b1

Tx prefix hash: bdb084f87887c9279d4f8180ae6da5479f4f78fc2e167bb68cdb38c2437bf844
Tx public key: 4321cf0f8c1e704cca58560e53edf9eb51a7cf8cc15d57708cec70857ee5a8d6
Timestamp: 1732897490 Timestamp [UCT]: 2024-11-29 16:24:50 Age [y:d:h:m:s]: 00:127:08:44:42
Block: 1164387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90827 RingCT/type: yes/0
Extra: 014321cf0f8c1e704cca58560e53edf9eb51a7cf8cc15d57708cec70857ee5a8d60211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9567a3e0738ad3939159d7d839c64ae47824823470adb3eed4a252e41ea8c4c6 0.600000000000 1650060 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": 1164397, "vin": [ { "gen": { "height": 1164387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9567a3e0738ad3939159d7d839c64ae47824823470adb3eed4a252e41ea8c4c6" } } ], "extra": [ 1, 67, 33, 207, 15, 140, 30, 112, 76, 202, 88, 86, 14, 83, 237, 249, 235, 81, 167, 207, 140, 193, 93, 87, 112, 140, 236, 112, 133, 126, 229, 168, 214, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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