Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab494351b7fa8dcddb3c83f9f09bb73401932df986ae7f9960d320731f97ba50

Tx prefix hash: b25f42970cbf2415788eb43f3199bb399026add84a0d540fa27f06f4c953a9a1
Tx public key: 85a45715bc217bfd8be1418561c0c0f29b72654360a27de760cbfb3f7d72ad96
Timestamp: 1742611144 Timestamp [UTC]: 2025-03-22 02:39:04 Age [y:d:h:m:s]: 01:242:16:44:18
Block: 1244535 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 437567 RingCT/type: yes/0
Extra: 0185a45715bc217bfd8be1418561c0c0f29b72654360a27de760cbfb3f7d72ad96021100000002e4dc9009000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f3da1dd1359feec85dffb9a470440fe53561e1b0360616be378e98f5fe8c6620 0.000600000000 1731526 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": 1244545, "vin": [ { "gen": { "height": 1244535 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3da1dd1359feec85dffb9a470440fe53561e1b0360616be378e98f5fe8c6620" } } ], "extra": [ 1, 133, 164, 87, 21, 188, 33, 123, 253, 139, 225, 65, 133, 97, 192, 192, 242, 155, 114, 101, 67, 96, 162, 125, 231, 96, 203, 251, 63, 125, 114, 173, 150, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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: