Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cfac29c546d67200bb68d09f2e7011bb0a72792f9bac7c1db27c72bdda909e0

Tx prefix hash: cd573ed9963b011e59be9f47b0f1011033ab97c7cd8e67d071efff43f9f0bfd1
Tx public key: f1f1c6ef9a3dfca2c31848d8e5dcc74ba9396a5d55f22ca3d3d978f8bc999e16
Timestamp: 1738392903 Timestamp [UTC]: 2025-02-01 06:55:03 Age [y:d:h:m:s]: 01:203:23:35:12
Block: 1209608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 410149 RingCT/type: yes/0
Extra: 01f1f1c6ef9a3dfca2c31848d8e5dcc74ba9396a5d55f22ca3d3d978f8bc999e160211000000031f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 88f233be72815334d60e0b837b04bfa8d874618ba28217737b40900424e560e2 0.000600000000 1696353 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": 1209618, "vin": [ { "gen": { "height": 1209608 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88f233be72815334d60e0b837b04bfa8d874618ba28217737b40900424e560e2" } } ], "extra": [ 1, 241, 241, 198, 239, 154, 61, 252, 162, 195, 24, 72, 216, 229, 220, 199, 75, 169, 57, 106, 93, 85, 242, 44, 163, 211, 217, 120, 248, 188, 153, 158, 22, 2, 17, 0, 0, 0, 3, 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: