Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3f0f3975adb44bddbe25db2b1f7335ef5e43fb4b60714affe92010bd4d842d4

Tx prefix hash: 05aebaf54b5d0eb3ca88534973dc753ab16b9581dfa4151eab4cdfa6bed1a58c
Tx public key: 32ac13ea0ddceedfcbb244c9c23feac8c4ed641a617aa3f5fa063941959a10af
Timestamp: 1773830080 Timestamp [UTC]: 2026-03-18 10:34:40 Age [y:d:h:m:s]: 00:242:10:37:23
Block: 1500423 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178744 RingCT/type: yes/0
Extra: 0132ac13ea0ddceedfcbb244c9c23feac8c4ed641a617aa3f5fa063941959a10af021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a1f159dbe9f6e2a81895bc775d714e00c447ab8ab11b054033bbc6e527f70b4f 0.000600000000 1990095 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": 1500433, "vin": [ { "gen": { "height": 1500423 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1f159dbe9f6e2a81895bc775d714e00c447ab8ab11b054033bbc6e527f70b4f" } } ], "extra": [ 1, 50, 172, 19, 234, 13, 220, 238, 223, 203, 178, 68, 201, 194, 63, 234, 200, 196, 237, 100, 26, 97, 122, 163, 245, 250, 6, 57, 65, 149, 154, 16, 175, 2, 17, 0, 0, 0, 2, 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: