Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a37ff68e391e10c3ff3df07eced79cdaf68d9834524938fe28306d7bb69c1ff

Tx prefix hash: 7f1c50f51ad632d37127ee1737cd048ed41fa4ae168e5d10bc9f9230f8662aba
Tx public key: b0f130b79dc7abdbc870563aa5c0b038c3ef661d3212bf281dd33f32fb9c0e69
Timestamp: 1708854097 Timestamp [UCT]: 2024-02-25 09:41:37 Age [y:d:h:m:s]: 01:027:17:27:11
Block: 965159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280811 RingCT/type: yes/0
Extra: 01b0f130b79dc7abdbc870563aa5c0b038c3ef661d3212bf281dd33f32fb9c0e690211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a4523d642ed1152d923a85c98da76235235d9d2b363e00bde92e29d84024701 0.600000000000 1424908 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": 965169, "vin": [ { "gen": { "height": 965159 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a4523d642ed1152d923a85c98da76235235d9d2b363e00bde92e29d84024701" } } ], "extra": [ 1, 176, 241, 48, 183, 157, 199, 171, 219, 200, 112, 86, 58, 165, 192, 176, 56, 195, 239, 102, 29, 50, 18, 191, 40, 29, 211, 63, 50, 251, 156, 14, 105, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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