Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6fbf3af6c7c915e2d0204cc559d86ad5cd630c20e026de0ced1bea396b9d2ce

Tx prefix hash: 8456009fe7bc30ebc3a9e3a0e77bd481f9b588d5de6f340cddbf8e3686fefcd8
Tx public key: 0d8fb9fead0857162603997db901e597f70561c29010a3e12f79ff54a4e019fc
Timestamp: 1746898763 Timestamp [UTC]: 2025-05-10 17:39:23 Age [y:d:h:m:s]: 01:191:20:01:59
Block: 1280027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401141 RingCT/type: yes/0
Extra: 010d8fb9fead0857162603997db901e597f70561c29010a3e12f79ff54a4e019fc0211000000019f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 794949bb0187e64d59c58a539cb1b38f34bb3d33c591c396acbbcfb8f658ddb2 0.000600000000 1767410 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": 1280037, "vin": [ { "gen": { "height": 1280027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "794949bb0187e64d59c58a539cb1b38f34bb3d33c591c396acbbcfb8f658ddb2" } } ], "extra": [ 1, 13, 143, 185, 254, 173, 8, 87, 22, 38, 3, 153, 125, 185, 1, 229, 151, 247, 5, 97, 194, 144, 16, 163, 225, 47, 121, 255, 84, 164, 224, 25, 252, 2, 17, 0, 0, 0, 1, 159, 159, 230, 140, 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: