Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf47054ac625b52940df37cb7400e5c6650ba366f9ea473c3df009c1e3195175

Tx prefix hash: a4f9520eb50076a9f5fca9288f50c7f062579c6aee1d50fb4e007484a27bb946
Tx public key: 1fa04d07761f74c94cb151a718f0643b72e53c61ad400d8e7bace1d78fa01c25
Timestamp: 1731321006 Timestamp [UCT]: 2024-11-11 10:30:06 Age [y:d:h:m:s]: 00:148:05:00:16
Block: 1151313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105761 RingCT/type: yes/0
Extra: 011fa04d07761f74c94cb151a718f0643b72e53c61ad400d8e7bace1d78fa01c25021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f8f54953df53be15057ac4349ccee40f8530aa171e50621f07ceda2e9f1cea5 0.600000000000 1636822 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": 1151323, "vin": [ { "gen": { "height": 1151313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f8f54953df53be15057ac4349ccee40f8530aa171e50621f07ceda2e9f1cea5" } } ], "extra": [ 1, 31, 160, 77, 7, 118, 31, 116, 201, 76, 177, 81, 167, 24, 240, 100, 59, 114, 229, 60, 97, 173, 64, 13, 142, 123, 172, 225, 215, 143, 160, 28, 37, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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