Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a473b1c2fe1d95c2dbbf42f1fd229d860b39f3bbef47b774f6acdc1287789374

Tx prefix hash: a916ee468203e655f367d16b0c4f0d7c72747edabb6b3d0c023aa35f4a8e705d
Tx public key: 22e1b48df0561846f5c2074e55ff8cfbfa4d5c2635e9aadfb9743a70e5ed1051
Timestamp: 1775094310 Timestamp [UTC]: 2026-04-02 01:45:10 Age [y:d:h:m:s]: 00:041:02:00:33
Block: 1510897 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 21670 RingCT/type: yes/0
Extra: 0122e1b48df0561846f5c2074e55ff8cfbfa4d5c2635e9aadfb9743a70e5ed1051021100000006ee4b7181000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 26b24d313af78ad071cf40f6bb92c591c2e3b3e59fcf6b9e4628cfe5f0ef7f7a 0.000600000000 2000683 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": 1510907, "vin": [ { "gen": { "height": 1510897 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26b24d313af78ad071cf40f6bb92c591c2e3b3e59fcf6b9e4628cfe5f0ef7f7a" } } ], "extra": [ 1, 34, 225, 180, 141, 240, 86, 24, 70, 245, 194, 7, 78, 85, 255, 140, 251, 250, 77, 92, 38, 53, 233, 170, 223, 185, 116, 58, 112, 229, 237, 16, 81, 2, 17, 0, 0, 0, 6, 238, 75, 113, 129, 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: