Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cab77fbb6ee7a3ccc4393176f8b584d4a0b37b90f0bde4f7029c735d65adf84

Tx prefix hash: 605a787a46d66fb9fa7803dc9822662a0b9a63733c6c36810fcecb2d81bb49ae
Tx public key: a4b8dae5efbfe9a328fc727c4e5c09964ab3ec5bc9efa8be7eefcf97d6b94803
Timestamp: 1770560229 Timestamp [UTC]: 2026-02-08 14:17:09 Age [y:d:h:m:s]: 00:006:22:41:52
Block: 1473416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 4930 RingCT/type: yes/0
Extra: 01a4b8dae5efbfe9a328fc727c4e5c09964ab3ec5bc9efa8be7eefcf97d6b94803020838e9513c0d888571

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 25a6ecf74858f0669fe6f3bc590dd9a0aeddd013eaa36ad2f562699b958cbe68 0.000600000000 1962698 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 dinastycoin-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": 1473426, "vin": [ { "gen": { "height": 1473416 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25a6ecf74858f0669fe6f3bc590dd9a0aeddd013eaa36ad2f562699b958cbe68" } } ], "extra": [ 1, 164, 184, 218, 229, 239, 191, 233, 163, 40, 252, 114, 124, 78, 92, 9, 150, 74, 179, 236, 91, 201, 239, 168, 190, 126, 239, 207, 151, 214, 185, 72, 3, 2, 8, 56, 233, 81, 60, 13, 136, 133, 113 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369