Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b25c42f2f46469da733a8d0df164a3deff6178634f91d1a6d238b7a6f83b689e

Tx prefix hash: 5bf0381c46d19759419c1bb5d6c7e8ff1921eceb4066e0bd58f69420a7471522
Tx public key: 6c4d0cb5e877cd9efee17618ad79f2b64d8bd8d432df07c9ca8955c14ca840c7
Timestamp: 1741210388 Timestamp [UTC]: 2025-03-05 21:33:08 Age [y:d:h:m:s]: 01:260:01:55:56
Block: 1232938 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 450069 RingCT/type: yes/0
Extra: 016c4d0cb5e877cd9efee17618ad79f2b64d8bd8d432df07c9ca8955c14ca840c70211000000011f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 014555f77e463e2e1706b6cccc092d8a21c4a956aca59233e3db679b6210463e 0.000600000000 1719855 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": 1232948, "vin": [ { "gen": { "height": 1232938 } } ], "vout": [ { "amount": 600000000, "target": { "key": "014555f77e463e2e1706b6cccc092d8a21c4a956aca59233e3db679b6210463e" } } ], "extra": [ 1, 108, 77, 12, 181, 232, 119, 205, 158, 254, 225, 118, 24, 173, 121, 242, 182, 77, 139, 216, 212, 50, 223, 7, 201, 202, 137, 85, 193, 76, 168, 64, 199, 2, 17, 0, 0, 0, 1, 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) | monero version: