Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d4d4fd5c75cc8663965cd71d4371f154060f8a207b1af6f41971479aad4aef0

Tx prefix hash: 9bc9ab7135beef18bd05e046503927cedcaf941e89e8f8b89209ff89a4c3d2ff
Tx public key: 094eab29264993ab7b1385af10caecebcda5aeee55d4c0abf95b09f309f6daef
Timestamp: 1729367436 Timestamp [UCT]: 2024-10-19 19:50:36 Age [y:d:h:m:s]: 00:170:08:16:59
Block: 1135212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121513 RingCT/type: yes/0
Extra: 01094eab29264993ab7b1385af10caecebcda5aeee55d4c0abf95b09f309f6daef0211000000013cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45a10d329e0f7b8bd60cb2b80f3a52e33a463bfe36016b760c6f1c258e7bd15e 0.600000000000 1618543 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 dinasty-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": 1135222, "vin": [ { "gen": { "height": 1135212 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45a10d329e0f7b8bd60cb2b80f3a52e33a463bfe36016b760c6f1c258e7bd15e" } } ], "extra": [ 1, 9, 78, 171, 41, 38, 73, 147, 171, 123, 19, 133, 175, 16, 202, 236, 235, 205, 165, 174, 238, 85, 212, 192, 171, 249, 91, 9, 243, 9, 246, 218, 239, 2, 17, 0, 0, 0, 1, 60, 208, 252, 6, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8