Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2220efb0991fcd166e83b702dad7117e4e28ebfbf560f0b9d72eff5dc1bd003

Tx prefix hash: 75e1a131d28a42209d5102e1ebfe371ce6dd7750fc1d247c953804d0353984f3
Tx public key: 6c7d1d47703436d7684baef6cb21390034fca2feff7256307c6785feaeac40c9
Timestamp: 1766283361 Timestamp [UTC]: 2025-12-21 02:16:01 Age [y:d:h:m:s]: 00:329:08:05:56
Block: 1438136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240691 RingCT/type: yes/0
Extra: 016c7d1d47703436d7684baef6cb21390034fca2feff7256307c6785feaeac40c9021100000002d6e19d7c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 17fe0617017a76682b6a6a7711ccb7d2ad000415c27f4c0d52eb6d70d9bda7ba 0.000600000000 1926953 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": 1438146, "vin": [ { "gen": { "height": 1438136 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17fe0617017a76682b6a6a7711ccb7d2ad000415c27f4c0d52eb6d70d9bda7ba" } } ], "extra": [ 1, 108, 125, 29, 71, 112, 52, 54, 215, 104, 75, 174, 246, 203, 33, 57, 0, 52, 252, 162, 254, 255, 114, 86, 48, 124, 103, 133, 254, 174, 172, 64, 201, 2, 17, 0, 0, 0, 2, 214, 225, 157, 124, 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: