Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 692af7c2a1f010fb9b82a3b8a0413f3e86ed1c9e3cc55afdc05c5e4bd9cbb16b

Tx prefix hash: 2be832013b341b1bf13a972040c593b2123cda6dca905c37124671d8fd225373
Tx public key: 0a08773ece16e5b1534fadb62c440412b200af2dca1f77fe05b7f80f20557af5
Timestamp: 1736094386 Timestamp [UTC]: 2025-01-05 16:26:26 Age [y:d:h:m:s]: 01:059:22:04:08
Block: 1190864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301125 RingCT/type: yes/0
Extra: 010a08773ece16e5b1534fadb62c440412b200af2dca1f77fe05b7f80f20557af50211000000031f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a0b803d49b5692d0dbfef6414ed5b3b7e75362c0549212bc5d933c4a96aebd3b 0.000600000000 1677385 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": 1190874, "vin": [ { "gen": { "height": 1190864 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0b803d49b5692d0dbfef6414ed5b3b7e75362c0549212bc5d933c4a96aebd3b" } } ], "extra": [ 1, 10, 8, 119, 62, 206, 22, 229, 177, 83, 79, 173, 182, 44, 68, 4, 18, 178, 0, 175, 45, 202, 31, 119, 254, 5, 183, 248, 15, 32, 85, 122, 245, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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) | dinastycoin version: tesla-369