Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f71325e8d583e00723de9b512f2d794f7efbff4020e0328d795fc74f4e973366

Tx prefix hash: 64bef90ff87f8a9a54a1927f891f9b3df374707faa1c53b88ae4a9c4b1c1aa38
Tx public key: c955761cd40e54deb45551d81dc313943c84fef9ff724929b617d15745d3a359
Timestamp: 1737944990 Timestamp [UTC]: 2025-01-27 02:29:50 Age [y:d:h:m:s]: 01:298:00:14:33
Block: 1205933 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477173 RingCT/type: yes/0
Extra: 01c955761cd40e54deb45551d81dc313943c84fef9ff724929b617d15745d3a3590211000000041f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 47c1bec51c87b5ce2e7cdfece4ba7480f66aa1e4e619bae004cb0598a820ad77 0.000600000000 1692632 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": 1205943, "vin": [ { "gen": { "height": 1205933 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47c1bec51c87b5ce2e7cdfece4ba7480f66aa1e4e619bae004cb0598a820ad77" } } ], "extra": [ 1, 201, 85, 118, 28, 212, 14, 84, 222, 180, 85, 81, 216, 29, 195, 19, 148, 60, 132, 254, 249, 255, 114, 73, 41, 182, 23, 209, 87, 69, 211, 163, 89, 2, 17, 0, 0, 0, 4, 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: