Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e63036da40b23e577b0903afd71a0ca32b2621b3ea0af027a7487281aecfb6f5

Tx prefix hash: 97aaec81acfc99fea6c1d0a422efd0aab8c6f664720f86f1fa115e8ace2e02e3
Tx public key: 9e398c60f4412d56e7eb457303fa14dd16668a3505f9e5b833191ff819aec68d
Timestamp: 1764092499 Timestamp [UCT]: 2025-11-25 17:41:39 Age [y:d:h:m:s]: 00:042:10:36:02
Block: 1419979 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30384 RingCT/type: yes/0
Extra: 019e398c60f4412d56e7eb457303fa14dd16668a3505f9e5b833191ff819aec68d021100000001fb8fd089000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd32412c83665bf1acd1e5965b3f79826091dcc30d311aa6e2293634105b5b1a 0.600000000000 1908520 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": 1419989, "vin": [ { "gen": { "height": 1419979 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd32412c83665bf1acd1e5965b3f79826091dcc30d311aa6e2293634105b5b1a" } } ], "extra": [ 1, 158, 57, 140, 96, 244, 65, 45, 86, 231, 235, 69, 115, 3, 250, 20, 221, 22, 102, 138, 53, 5, 249, 229, 184, 51, 25, 31, 248, 25, 174, 198, 141, 2, 17, 0, 0, 0, 1, 251, 143, 208, 137, 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