Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88afe77fd2517d0093686f0d5072de82938045a4080f155ca47e678826b578d5

Tx prefix hash: f377c2028771df37d3cc29ef724a8bd3b6a7d785b2956e6bbddec78c23e4e3da
Tx public key: f05d6ecc1fb29fe511d3225688993920f1cd253e2b765123c7d0c80fb8cb3221
Timestamp: 1703285312 Timestamp [UCT]: 2023-12-22 22:48:32 Age [y:d:h:m:s]: 01:176:00:34:51
Block: 918984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 386873 RingCT/type: yes/0
Extra: 01f05d6ecc1fb29fe511d3225688993920f1cd253e2b765123c7d0c80fb8cb322102110000000f59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b7dfdc9136ac05fe199955c2ed5081e503d45de1cc1982cab2cec6ab04725da 0.600000000000 1376648 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": 918994, "vin": [ { "gen": { "height": 918984 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b7dfdc9136ac05fe199955c2ed5081e503d45de1cc1982cab2cec6ab04725da" } } ], "extra": [ 1, 240, 93, 110, 204, 31, 178, 159, 229, 17, 211, 34, 86, 136, 153, 57, 32, 241, 205, 37, 62, 43, 118, 81, 35, 199, 208, 200, 15, 184, 203, 50, 33, 2, 17, 0, 0, 0, 15, 89, 218, 211, 245, 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