Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df6072e482f1608e9f7524b0e178a8c530c44545b7fd549de2b86af66ebd99cc

Tx prefix hash: 81b1991ec554a5a417e0b3ae8e62e5b86969b21819dff0d04ae1e61707bb254d
Tx public key: 6ef19fb968d3328c4e2076c2841d5fdb3ca8b9398a0c6ef53f5fdb8115b399a2
Timestamp: 1740446778 Timestamp [UTC]: 2025-02-25 01:26:18 Age [y:d:h:m:s]: 01:077:10:37:41
Block: 1226591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306238 RingCT/type: yes/0
Extra: 016ef19fb968d3328c4e2076c2841d5fdb3ca8b9398a0c6ef53f5fdb8115b399a2021100000001007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 03b8f34402215587ab2268ae1e7584c3d1650b313071eed2c18c589845654b6c 0.000600000000 1713464 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": 1226601, "vin": [ { "gen": { "height": 1226591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03b8f34402215587ab2268ae1e7584c3d1650b313071eed2c18c589845654b6c" } } ], "extra": [ 1, 110, 241, 159, 185, 104, 211, 50, 140, 78, 32, 118, 194, 132, 29, 95, 219, 60, 168, 185, 57, 138, 12, 110, 245, 63, 95, 219, 129, 21, 179, 153, 162, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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: