Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a71d35767f1b93f1449751fa9dedf841d6bd54def182996af65f97cff512c13

Tx prefix hash: 795eec1600d6b3fb330e256797ec7a6c4e5a971be72a505dd8d2bd2f0678c457
Tx public key: 6fa925f9789040efc0eb5e91daa696e06f76215924ce2efab77541b3c363ca23
Timestamp: 1758103649 Timestamp [UTC]: 2025-09-17 10:07:29 Age [y:d:h:m:s]: 01:066:09:42:54
Block: 1370350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313800 RingCT/type: yes/0
Extra: 016fa925f9789040efc0eb5e91daa696e06f76215924ce2efab77541b3c363ca2302110000000cb2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7db26f78406cbea7bb2ace13cfe18f42b20c5fa1ad4cb4788f0e6713eeb8ed17 0.000600000000 1858425 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": 1370360, "vin": [ { "gen": { "height": 1370350 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7db26f78406cbea7bb2ace13cfe18f42b20c5fa1ad4cb4788f0e6713eeb8ed17" } } ], "extra": [ 1, 111, 169, 37, 249, 120, 144, 64, 239, 192, 235, 94, 145, 218, 166, 150, 224, 111, 118, 33, 89, 36, 206, 46, 250, 183, 117, 65, 179, 195, 99, 202, 35, 2, 17, 0, 0, 0, 12, 178, 247, 132, 196, 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: