Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c190d38347fb9be8b552d48a5fae5f3b69fd24372cbe388e351cd593eb6e093

Tx prefix hash: bd0cd6a4e75fb0ac45abe31c4d5f665cf228f1983219772fcfe423b44d50366a
Tx public key: 2dbac0c7a01323515c97c4d24e75a4f8cc0d12483e4c7293d466dcafee4c9124
Timestamp: 1739962226 Timestamp [UCT]: 2025-02-19 10:50:26 Age [y:d:h:m:s]: 00:231:16:46:50
Block: 1222572 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163331 RingCT/type: yes/0
Extra: 012dbac0c7a01323515c97c4d24e75a4f8cc0d12483e4c7293d466dcafee4c91240211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52786867b66c79e8268a6bab8c7c675b78eb137b20d5de653aa9d378921c874f 0.600000000000 1709423 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": 1222582, "vin": [ { "gen": { "height": 1222572 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52786867b66c79e8268a6bab8c7c675b78eb137b20d5de653aa9d378921c874f" } } ], "extra": [ 1, 45, 186, 192, 199, 160, 19, 35, 81, 92, 151, 196, 210, 78, 117, 164, 248, 204, 13, 18, 72, 62, 76, 114, 147, 212, 102, 220, 175, 238, 76, 145, 36, 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