Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb73a7a09f2216434e6b0cd03ae78e52fd9b3900009e02f0dc5aac5333ce3721

Tx prefix hash: ece35c9c27cb8a36954f459b03e7ce60e446c98d3f49e69e8958c1717afd54ca
Tx public key: 7ff3e61b5f385bd8a1e701db3b3f60df95877ff72976ddc72699ec579c2e308e
Timestamp: 1582194865 Timestamp [UTC]: 2020-02-20 10:34:25 Age [y:d:h:m:s]: 06:273:04:57:59
Block: 68745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1612470 RingCT/type: yes/0
Extra: 017ff3e61b5f385bd8a1e701db3b3f60df95877ff72976ddc72699ec579c2e308e0211000000017adf42d3000000000000000000

1 output(s) for total of 0.363280904866 xmr

stealth address amount amount idx tag
00: 99206ab6de1a7700f39a38276a5e8b4b56d069e4804f420413a39c0db61dfe46 0.363280904866 126734 of 0 -

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": 68755, "vin": [ { "gen": { "height": 68745 } } ], "vout": [ { "amount": 363280904866, "target": { "key": "99206ab6de1a7700f39a38276a5e8b4b56d069e4804f420413a39c0db61dfe46" } } ], "extra": [ 1, 127, 243, 230, 27, 95, 56, 91, 216, 161, 231, 1, 219, 59, 63, 96, 223, 149, 135, 127, 247, 41, 118, 221, 199, 38, 153, 236, 87, 156, 46, 48, 142, 2, 17, 0, 0, 0, 1, 122, 223, 66, 211, 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: