Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8bd75fff63833837b5beb7195128cf98de12226bee8aebee4f64156f87c86eb3

Tx prefix hash: 2ae94bb7c08faf962c9070419758a8f03a878804bf0555b954fed0931733011e
Tx public key: 81f463ce762b95d3ccb2e9bed9cb270f7500bbef3cea5afbcadb857c49b42e53
Timestamp: 1767445847 Timestamp [UTC]: 2026-01-03 13:10:47 Age [y:d:h:m:s]: 00:044:03:30:07
Block: 1447768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 31403 RingCT/type: yes/0
Extra: 0181f463ce762b95d3ccb2e9bed9cb270f7500bbef3cea5afbcadb857c49b42e53020900000007f3b3285400

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3ecb4cf69c58d380de300e031578a1e9e28681d29b55e7fad5ac3d5fe4d9a72f 0.000600000000 1936728 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": 1447778, "vin": [ { "gen": { "height": 1447768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ecb4cf69c58d380de300e031578a1e9e28681d29b55e7fad5ac3d5fe4d9a72f" } } ], "extra": [ 1, 129, 244, 99, 206, 118, 43, 149, 211, 204, 178, 233, 190, 217, 203, 39, 15, 117, 0, 187, 239, 60, 234, 90, 251, 202, 219, 133, 124, 73, 180, 46, 83, 2, 9, 0, 0, 0, 7, 243, 179, 40, 84, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369