Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8566e89ca5b542b6b53922355695e6dc502e57537b0ea7aa89e7d3d609fef653

Tx prefix hash: 9ec3ec3ca93670a76950612d80cbd76fb817587af17a3801d59cefb96339efa7
Tx public key: 5e222bd564bdf01c5d6ddb4a222485ead1fc276e70876f532f3175d2a4ee9bd6
Timestamp: 1709442135 Timestamp [UCT]: 2024-03-03 05:02:15 Age [y:d:h:m:s]: 01:256:08:38:36
Block: 970034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 441944 RingCT/type: yes/0
Extra: 015e222bd564bdf01c5d6ddb4a222485ead1fc276e70876f532f3175d2a4ee9bd602110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 431e3cd6253bb80dac674035ff5b919208aedd4e7b251fe03b7deb102bc1d1dc 0.600000000000 1429883 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": 970044, "vin": [ { "gen": { "height": 970034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "431e3cd6253bb80dac674035ff5b919208aedd4e7b251fe03b7deb102bc1d1dc" } } ], "extra": [ 1, 94, 34, 43, 213, 100, 189, 240, 28, 93, 109, 219, 74, 34, 36, 133, 234, 209, 252, 39, 110, 112, 135, 111, 83, 47, 49, 117, 210, 164, 238, 155, 214, 2, 17, 0, 0, 0, 10, 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