Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61b8a54d464903a645d47871dbe20842a4da31ab9558fa7cddbca0cc26a45d99

Tx prefix hash: b42dcfd752988e5ce42aff34834a68cbcf6254f0722e9e7c63ca0b56081901be
Tx public key: 40defe139cd4b0db6d766fb368c7518e7a3c5ab9a8ca995cd35c9fecfa0caa10
Timestamp: 1775202330 Timestamp [UTC]: 2026-04-03 07:45:30 Age [y:d:h:m:s]: 00:230:17:56:19
Block: 1511790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170517 RingCT/type: yes/0
Extra: 0140defe139cd4b0db6d766fb368c7518e7a3c5ab9a8ca995cd35c9fecfa0caa10021100000002e3d7dc9f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 65086afa8aad4c9787dfe5ae9b0a3c352a0296360153d7b3aaaa9fd5c0deb7f6 0.000600000000 2001584 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": 1511800, "vin": [ { "gen": { "height": 1511790 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65086afa8aad4c9787dfe5ae9b0a3c352a0296360153d7b3aaaa9fd5c0deb7f6" } } ], "extra": [ 1, 64, 222, 254, 19, 156, 212, 176, 219, 109, 118, 111, 179, 104, 199, 81, 142, 122, 60, 90, 185, 168, 202, 153, 92, 211, 92, 159, 236, 250, 12, 170, 16, 2, 17, 0, 0, 0, 2, 227, 215, 220, 159, 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: