Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75047d1765b78fb152438ab3d27467e6bc9db2b67c7927bcf1df4c2bcb9ca2a1

Tx prefix hash: 1d5344ee28fe6200dec9b8a33c29c13cbff906e1afcef6464c624010b8f66da7
Tx public key: 29ffc2c3308e4a8371301fe56773f80f78f04c27b5bfb05437e784e814ccafdb
Timestamp: 1740588232 Timestamp [UTC]: 2025-02-26 16:43:52 Age [y:d:h:m:s]: 01:076:19:52:53
Block: 1227782 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305821 RingCT/type: yes/0
Extra: 0129ffc2c3308e4a8371301fe56773f80f78f04c27b5bfb05437e784e814ccafdb02110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8fb8de5d412c14cdeaf44fccea896a9034d07f5ba7e1f4d1dbc871b97374f143 0.000600000000 1714657 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": 1227792, "vin": [ { "gen": { "height": 1227782 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8fb8de5d412c14cdeaf44fccea896a9034d07f5ba7e1f4d1dbc871b97374f143" } } ], "extra": [ 1, 41, 255, 194, 195, 48, 142, 74, 131, 113, 48, 31, 229, 103, 115, 248, 15, 120, 240, 76, 39, 181, 191, 176, 84, 55, 231, 132, 232, 20, 204, 175, 219, 2, 17, 0, 0, 0, 10, 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: