Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba003b92cc3bc461d79c95e217a96ec6f6d2b67f758585fb1008ca4e8ab43225

Tx prefix hash: 5a1d7156b776d8b4b279cb319fdc81f2e05cbd945b4d49c98ff7c83740491749
Tx public key: 1ebb4edd8aabf6a549911c1af954001d809f71210b863c022cc7358aabb4b799
Timestamp: 1770394104 Timestamp [UTC]: 2026-02-06 16:08:24 Age [y:d:h:m:s]: 00:007:20:01:21
Block: 1472035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 5578 RingCT/type: yes/0
Extra: 011ebb4edd8aabf6a549911c1af954001d809f71210b863c022cc7358aabb4b799020886b533bd48602a94

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 56f5dd32200c17c0d40f68800be6c05b5bdd1bf307f25f77fb5869cf9dc9da21 0.000600000000 1961311 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": 1472045, "vin": [ { "gen": { "height": 1472035 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56f5dd32200c17c0d40f68800be6c05b5bdd1bf307f25f77fb5869cf9dc9da21" } } ], "extra": [ 1, 30, 187, 78, 221, 138, 171, 246, 165, 73, 145, 28, 26, 249, 84, 0, 29, 128, 159, 113, 33, 11, 134, 60, 2, 44, 199, 53, 138, 171, 180, 183, 153, 2, 8, 134, 181, 51, 189, 72, 96, 42, 148 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369