Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 655cab810f021c117c8dfd45099b3deaaa205a4f8054e7c831f39910f7773e43

Tx prefix hash: 65ad1da74e774ab552a4dcd2581453a70771947be89e3aa15439276794e0004f
Tx public key: f1040044b45ed704f3a3d5837e508af362ced1277b5bf6145c4f60a2a357952b
Timestamp: 1739935340 Timestamp [UTC]: 2025-02-19 03:22:20 Age [y:d:h:m:s]: 01:272:21:38:47
Block: 1222355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 459164 RingCT/type: yes/0
Extra: 01f1040044b45ed704f3a3d5837e508af362ced1277b5bf6145c4f60a2a357952b021100000003007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 65d0c17eb5e8bea1b8e4a1eae464abc26a285f0e416484e8ad1887c4367ded2c 0.000600000000 1709206 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": 1222365, "vin": [ { "gen": { "height": 1222355 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65d0c17eb5e8bea1b8e4a1eae464abc26a285f0e416484e8ad1887c4367ded2c" } } ], "extra": [ 1, 241, 4, 0, 68, 180, 94, 215, 4, 243, 163, 213, 131, 126, 80, 138, 243, 98, 206, 209, 39, 123, 91, 246, 20, 92, 79, 96, 162, 163, 87, 149, 43, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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: