Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e4704a932e84ca5d497cc0de6837beaea61a3194ba2a2750a948510d8f539c7

Tx prefix hash: 3bb391ecce08d7319fe3e743cdd7ecb731e309b7b626b72e49d651da80785542
Tx public key: 6a220fa23986494f4aeafdcdffaae6eba4808b5fe2d8d790b317f0971cf933e1
Timestamp: 1732445325 Timestamp [UCT]: 2024-11-24 10:48:45 Age [y:d:h:m:s]: 00:138:05:19:09
Block: 1160634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98614 RingCT/type: yes/0
Extra: 016a220fa23986494f4aeafdcdffaae6eba4808b5fe2d8d790b317f0971cf933e1021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 394fe3d78177f93c61aa997559fafd16d06ea1d56174d2e1a035e3b3d84b1560 0.600000000000 1646281 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": 1160644, "vin": [ { "gen": { "height": 1160634 } } ], "vout": [ { "amount": 600000000, "target": { "key": "394fe3d78177f93c61aa997559fafd16d06ea1d56174d2e1a035e3b3d84b1560" } } ], "extra": [ 1, 106, 34, 15, 162, 57, 134, 73, 79, 74, 234, 253, 205, 255, 170, 230, 235, 164, 128, 139, 95, 226, 216, 215, 144, 179, 23, 240, 151, 28, 249, 51, 225, 2, 17, 0, 0, 0, 1, 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