Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b080dd440589d9364fe77832197af832fab4cef4c6a6891d53156c13b9e1a21f

Tx prefix hash: 43c983275e8cc210c245fbe3d46412138e318f03ffcfb7adeee44b1f2773bc04
Tx public key: 4688585e191a8dd7af4537e914b30183d1f71558d857c264991b52a517e37df8
Timestamp: 1735257467 Timestamp [UCT]: 2024-12-26 23:57:47 Age [y:d:h:m:s]: 00:088:12:57:05
Block: 1183926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63059 RingCT/type: yes/0
Extra: 014688585e191a8dd7af4537e914b30183d1f71558d857c264991b52a517e37df80211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa5a0137aa6adc0d0a7d0bed86b3ef2366483572f358d7790bcc4b3994cfe4f6 0.600000000000 1670375 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": 1183936, "vin": [ { "gen": { "height": 1183926 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa5a0137aa6adc0d0a7d0bed86b3ef2366483572f358d7790bcc4b3994cfe4f6" } } ], "extra": [ 1, 70, 136, 88, 94, 25, 26, 141, 215, 175, 69, 55, 233, 20, 179, 1, 131, 209, 247, 21, 88, 216, 87, 194, 100, 153, 27, 82, 165, 23, 227, 125, 248, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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