Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2996ea5012c33c7f2cb537818107e10597e0617c82b9399ebfb0c434837dc4f1

Tx prefix hash: 57ead7a2e2c50bcf621d5ab45252c814a3f2effab8b77c4e0a536c00f1306f21
Tx public key: 0980ee6a10c816c94aa20524acf68b16b46eb4a23a19f4e8f5115c37b592489d
Timestamp: 1774384954 Timestamp [UTC]: 2026-03-24 20:42:34 Age [y:d:h:m:s]: 00:241:06:19:15
Block: 1505027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178091 RingCT/type: yes/0
Extra: 010980ee6a10c816c94aa20524acf68b16b46eb4a23a19f4e8f5115c37b592489d021100000007f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8363f717644e4eb8c994a074205ad045c739377ad0ffc890e266c78d563c5e46 0.000600000000 1994757 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": 1505037, "vin": [ { "gen": { "height": 1505027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8363f717644e4eb8c994a074205ad045c739377ad0ffc890e266c78d563c5e46" } } ], "extra": [ 1, 9, 128, 238, 106, 16, 200, 22, 201, 74, 162, 5, 36, 172, 246, 139, 22, 180, 110, 180, 162, 58, 25, 244, 232, 245, 17, 92, 55, 181, 146, 72, 157, 2, 17, 0, 0, 0, 7, 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: