Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2ee5449bc2152bf2295f87ae92c6c83188c0f6a8c7a6a289d12aece7f3be7c0

Tx prefix hash: 4554e704fe14644344be6741b9faf72d4193d9bdf7fb369f878fa37a6ddf0e9e
Tx public key: dd0645b0baaaf912cc3d2028293329ebe4729f4081330156986ac4d9cd08c91b
Timestamp: 1771514073 Timestamp [UTC]: 2026-02-19 15:14:33 Age [y:d:h:m:s]: 00:274:09:58:34
Block: 1481284 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201785 RingCT/type: yes/0
Extra: 01dd0645b0baaaf912cc3d2028293329ebe4729f4081330156986ac4d9cd08c91b021100000005f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1f36f58e2de4818628a07cd6da2df8b3a2ed88f5005ce9854e0feff9e3d90264 0.000600000000 1970660 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": 1481294, "vin": [ { "gen": { "height": 1481284 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f36f58e2de4818628a07cd6da2df8b3a2ed88f5005ce9854e0feff9e3d90264" } } ], "extra": [ 1, 221, 6, 69, 176, 186, 170, 249, 18, 204, 61, 32, 40, 41, 51, 41, 235, 228, 114, 159, 64, 129, 51, 1, 86, 152, 106, 196, 217, 205, 8, 201, 27, 2, 17, 0, 0, 0, 5, 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: