Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 929ce2db4f2e57dd5eb9658581e0068c3dcdd20c6230168ad6f823973d10ea89

Tx prefix hash: 5ab30740cc88dcc131d7077ce74d633570e0439be34c9d765ed9770b74f7f736
Tx public key: 87cb22413b244e0fd1724d3f434516ee27051fbd69012b4bc0ab40d42a4f76f9
Timestamp: 1768119176 Timestamp [UTC]: 2026-01-11 08:12:56 Age [y:d:h:m:s]: 00:034:20:07:46
Block: 1453356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24742 RingCT/type: yes/0
Extra: 0187cb22413b244e0fd1724d3f434516ee27051fbd69012b4bc0ab40d42a4f76f9021100000001215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c50311535dcc59a0c17ad04ba63dd04baa41c0f85f101e34cc7ea89ee1dd1fb6 0.000600000000 1942408 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": 1453366, "vin": [ { "gen": { "height": 1453356 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c50311535dcc59a0c17ad04ba63dd04baa41c0f85f101e34cc7ea89ee1dd1fb6" } } ], "extra": [ 1, 135, 203, 34, 65, 59, 36, 78, 15, 209, 114, 77, 63, 67, 69, 22, 238, 39, 5, 31, 189, 105, 1, 43, 75, 192, 171, 64, 212, 42, 79, 118, 249, 2, 17, 0, 0, 0, 1, 33, 91, 191, 137, 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) | dinastycoin version: tesla-369