Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a7c44c1748e45846eb857df19bf7be066cabdc05f58920c5ff5d77bdfe48409

Tx prefix hash: 997c79132e2d4531c33014ff3f392c023e6b3e474b7c4b51a90eb27269384672
Tx public key: bacf72196f11fd62cb1a1be1baece740571dd51b68084d34db2335bf11cf6750
Timestamp: 1771948017 Timestamp [UTC]: 2026-02-24 15:46:57 Age [y:d:h:m:s]: 00:266:14:29:07
Block: 1484883 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196047 RingCT/type: yes/0
Extra: 01bacf72196f11fd62cb1a1be1baece740571dd51b68084d34db2335bf11cf6750021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: dfc32e6f8f3c501b2aeb626519a3aa845a8a5d2c77e696863423dc669af26079 0.000600000000 1974315 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": 1484893, "vin": [ { "gen": { "height": 1484883 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dfc32e6f8f3c501b2aeb626519a3aa845a8a5d2c77e696863423dc669af26079" } } ], "extra": [ 1, 186, 207, 114, 25, 111, 17, 253, 98, 203, 26, 27, 225, 186, 236, 231, 64, 87, 29, 213, 27, 104, 8, 77, 52, 219, 35, 53, 191, 17, 207, 103, 80, 2, 17, 0, 0, 0, 3, 241, 136, 200, 168, 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: