Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcbf33fe63f40fe03474c1a7d69556e816a60a6172c686b2735ffd3696bbbfcb

Tx prefix hash: 38aa56d1a4f2fe313a7e361e94de13b43a710e654eb12be1136cade71ad4e387
Tx public key: 088b43f4571fb75b3aec6de28a637ea1821c4ac26a978d36be180a67691e9a77
Timestamp: 1735399590 Timestamp [UCT]: 2024-12-28 15:26:30 Age [y:d:h:m:s]: 00:095:12:03:33
Block: 1185086 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68043 RingCT/type: yes/0
Extra: 01088b43f4571fb75b3aec6de28a637ea1821c4ac26a978d36be180a67691e9a770211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e44c2e37cbc71fb9b70aafdef244046879e272a84afb6d65b4b6ac308387cc04 0.600000000000 1671551 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": 1185096, "vin": [ { "gen": { "height": 1185086 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e44c2e37cbc71fb9b70aafdef244046879e272a84afb6d65b4b6ac308387cc04" } } ], "extra": [ 1, 8, 139, 67, 244, 87, 31, 183, 91, 58, 236, 109, 226, 138, 99, 126, 161, 130, 28, 74, 194, 106, 151, 141, 54, 190, 24, 10, 103, 105, 30, 154, 119, 2, 17, 0, 0, 0, 2, 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