Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76c017b5d89f485350ad9ef0b3efd9df6b3aacbcfe0a89f1c5edacea4110affb

Tx prefix hash: 8b14d5a2e005e15e1319f0c17c51929754a202562b6bc37b27136255e62ec5d2
Tx public key: 6f266f524dbb0ee608b183c1e94839f58ed57a6c17d039786595fc7439c73a21
Timestamp: 1763184670 Timestamp [UCT]: 2025-11-15 05:31:10 Age [y:d:h:m:s]: 00:038:18:46:11
Block: 1412451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27764 RingCT/type: yes/0
Extra: 016f266f524dbb0ee608b183c1e94839f58ed57a6c17d039786595fc7439c73a21021100000003d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1919eb19e96643db5056f4bc09e8fbe9bba44a8fc73866bf5bf0c5f69fd9329 0.600000000000 1900920 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": 1412461, "vin": [ { "gen": { "height": 1412451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1919eb19e96643db5056f4bc09e8fbe9bba44a8fc73866bf5bf0c5f69fd9329" } } ], "extra": [ 1, 111, 38, 111, 82, 77, 187, 14, 230, 8, 177, 131, 193, 233, 72, 57, 245, 142, 213, 122, 108, 23, 208, 57, 120, 101, 149, 252, 116, 57, 199, 58, 33, 2, 17, 0, 0, 0, 3, 214, 225, 157, 124, 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