Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b906745cead4b5dbb5ce48a477b7cbd08abdd5dda17e24b5e9253783ba9e241c

Tx prefix hash: 043e1bea84d8d672b2598f48da8ebb5e36ee02669e8b1ab80c32eab6aa5d0ffd
Tx public key: a7c351372a09618db04a5b5d3ec77de5fea13a5813b0110c2c02a258d05dd985
Timestamp: 1740546563 Timestamp [UTC]: 2025-02-26 05:09:23 Age [y:d:h:m:s]: 01:267:01:49:00
Block: 1227431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 455057 RingCT/type: yes/0
Extra: 01a7c351372a09618db04a5b5d3ec77de5fea13a5813b0110c2c02a258d05dd9850211000000071f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 819b45007e9aa8634b2039b09f38f6f1ba85641d0b593eac5e1ab06031a247c0 0.000600000000 1714304 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": 1227441, "vin": [ { "gen": { "height": 1227431 } } ], "vout": [ { "amount": 600000000, "target": { "key": "819b45007e9aa8634b2039b09f38f6f1ba85641d0b593eac5e1ab06031a247c0" } } ], "extra": [ 1, 167, 195, 81, 55, 42, 9, 97, 141, 176, 74, 91, 93, 62, 199, 125, 229, 254, 161, 58, 88, 19, 176, 17, 12, 44, 2, 162, 88, 208, 93, 217, 133, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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: