Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ea940279def3f1f0c705aeafb386bf3510778c035d5f2aa6c78a1e180b4fc76

Tx prefix hash: 850f40b3ffb67eb09386f7aa52a0b73ece61aee1ef2d75c97d3520c0e45b322c
Tx public key: ec2d880fd2b59501ed91bd4e98864590f42c4b0b50e1e9b2006ae0fa55bce9a5
Timestamp: 1772323449 Timestamp [UTC]: 2026-03-01 00:04:09 Age [y:d:h:m:s]: 00:265:08:37:14
Block: 1487973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195317 RingCT/type: yes/0
Extra: 01ec2d880fd2b59501ed91bd4e98864590f42c4b0b50e1e9b2006ae0fa55bce9a5021100000005e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: daf64c57647908f6349dfabda3ff2ac80ae4e19e8af274ad2fc34ceb6e5f20dd 0.000600000000 1977449 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": 1487983, "vin": [ { "gen": { "height": 1487973 } } ], "vout": [ { "amount": 600000000, "target": { "key": "daf64c57647908f6349dfabda3ff2ac80ae4e19e8af274ad2fc34ceb6e5f20dd" } } ], "extra": [ 1, 236, 45, 136, 15, 210, 181, 149, 1, 237, 145, 189, 78, 152, 134, 69, 144, 244, 44, 75, 11, 80, 225, 233, 178, 0, 106, 224, 250, 85, 188, 233, 165, 2, 17, 0, 0, 0, 5, 228, 245, 25, 63, 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: