Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 020f909ba42c8367c4ea95ff636ce356edd87f90ba7990c78700a0597e11bc51

Tx prefix hash: a81039b4a32fcd17ee7ea2d72464b6dba6443bc48d90d6d4221b0a08ec78de5d
Tx public key: 039fb8cb9243deb5a4385d33ff93ea17be5140734dea5c37f9037fbf45db5644
Timestamp: 1774767713 Timestamp [UTC]: 2026-03-29 07:01:53 Age [y:d:h:m:s]: 00:234:08:45:38
Block: 1508205 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173016 RingCT/type: yes/0
Extra: 01039fb8cb9243deb5a4385d33ff93ea17be5140734dea5c37f9037fbf45db5644021100000006f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a4c8166fbaa4640eaf90a6d316578ccb9cdfd2b128bb569fdf9a1668d743daa3 0.000600000000 1997957 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": 1508215, "vin": [ { "gen": { "height": 1508205 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4c8166fbaa4640eaf90a6d316578ccb9cdfd2b128bb569fdf9a1668d743daa3" } } ], "extra": [ 1, 3, 159, 184, 203, 146, 67, 222, 181, 164, 56, 93, 51, 255, 147, 234, 23, 190, 81, 64, 115, 77, 234, 92, 55, 249, 3, 127, 191, 69, 219, 86, 68, 2, 17, 0, 0, 0, 6, 241, 136, 200, 168, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


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