Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be17aaca2a496ef5370badb05e3a973b85ff1ce1f62d1099db08a000a364f329

Tx prefix hash: d1cb999008e19ee5b89ca2748ce0099629b98265c6780d3e9280f0689575f5a5
Tx public key: e80277e7b735fe81adfae84f4b8a03c4b293dc7be88cc225814c6a58b5de63ed
Timestamp: 1729153042 Timestamp [UCT]: 2024-10-17 08:17:22 Age [y:d:h:m:s]: 00:098:06:18:19
Block: 1133436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70196 RingCT/type: yes/0
Extra: 01e80277e7b735fe81adfae84f4b8a03c4b293dc7be88cc225814c6a58b5de63ed0211000000043cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: faec0acaf014968b1dc325b7e14828a5159eeba61530831e9bb9a864b2ae5f70 0.600000000000 1616553 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": 1133446, "vin": [ { "gen": { "height": 1133436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "faec0acaf014968b1dc325b7e14828a5159eeba61530831e9bb9a864b2ae5f70" } } ], "extra": [ 1, 232, 2, 119, 231, 183, 53, 254, 129, 173, 250, 232, 79, 75, 138, 3, 196, 178, 147, 220, 123, 232, 140, 194, 37, 129, 76, 106, 88, 181, 222, 99, 237, 2, 17, 0, 0, 0, 4, 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