Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e15aaac395dee351a0e7ef8e554e698761cbebe2beb4024f9459021a5477976

Tx prefix hash: 764a43e824594153eed17a0c3546b03b7cececf48e682c974e0409603d2a05ae
Tx public key: b02f4e5ded6fc39ecaec3498731aef9d555c13e22249ff2d0f244f486eb0b9bd
Timestamp: 1768971997 Timestamp [UTC]: 2026-01-21 05:06:37 Age [y:d:h:m:s]: 00:305:02:43:05
Block: 1460263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223231 RingCT/type: yes/0
Extra: 01b02f4e5ded6fc39ecaec3498731aef9d555c13e22249ff2d0f244f486eb0b9bd02110000000349d73e98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 47a3d20e2f3cd3a007fb346296b2290dc0d09b80fc0c6538a38858e3a601b050 0.000600000000 1949433 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": 1460273, "vin": [ { "gen": { "height": 1460263 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47a3d20e2f3cd3a007fb346296b2290dc0d09b80fc0c6538a38858e3a601b050" } } ], "extra": [ 1, 176, 47, 78, 93, 237, 111, 195, 158, 202, 236, 52, 152, 115, 26, 239, 157, 85, 92, 19, 226, 34, 73, 255, 45, 15, 36, 79, 72, 110, 176, 185, 189, 2, 17, 0, 0, 0, 3, 73, 215, 62, 152, 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: