Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7dca440c939f857865fc2fcb04464ffc095bbe3065f2ea541f783946c9a0c2ba

Tx prefix hash: 97bf39559ada03a6ac4a057b3ff3470a6a4c1ddf2a251d39f35c3ac68b26630e
Tx public key: 368a177649f47e5d08c3f2c95ff0f784e451740a7b930fecd492d5937e8237f0
Timestamp: 1739913281 Timestamp [UTC]: 2025-02-18 21:14:41 Age [y:d:h:m:s]: 01:271:03:42:55
Block: 1222182 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457853 RingCT/type: yes/0
Extra: 01368a177649f47e5d08c3f2c95ff0f784e451740a7b930fecd492d5937e8237f00211000000011f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b9039f9e5bf33873a2522ecab1d53a4a30065b8b84e6fd3a6b07ecc7b78f8246 0.000600000000 1709031 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": 1222192, "vin": [ { "gen": { "height": 1222182 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9039f9e5bf33873a2522ecab1d53a4a30065b8b84e6fd3a6b07ecc7b78f8246" } } ], "extra": [ 1, 54, 138, 23, 118, 73, 244, 126, 93, 8, 195, 242, 201, 95, 240, 247, 132, 228, 81, 116, 10, 123, 147, 15, 236, 212, 146, 213, 147, 126, 130, 55, 240, 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: