Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cff6b89900cc946c881e5be3a7dfc1610a1252b9e0a19494043ddf723ed1d11

Tx prefix hash: 2fb4f0d746b69b31b2f9856ad77a706579487a4ff7088436d3831304c616e8c4
Tx public key: f743e48f699b5fb8d89cc95f380a2a5f34410e4fb5eed0c90cf64856fface44b
Timestamp: 1714011198 Timestamp [UCT]: 2024-04-25 02:13:18 Age [y:d:h:m:s]: 00:357:19:50:37
Block: 1007897 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255799 RingCT/type: yes/0
Extra: 01f743e48f699b5fb8d89cc95f380a2a5f34410e4fb5eed0c90cf64856fface44b02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85ca1cca977fd04e793d2c305879ace79ba1022ad1923d7a253c31f066c5051b 0.600000000000 1469363 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": 1007907, "vin": [ { "gen": { "height": 1007897 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85ca1cca977fd04e793d2c305879ace79ba1022ad1923d7a253c31f066c5051b" } } ], "extra": [ 1, 247, 67, 228, 143, 105, 155, 95, 184, 216, 156, 201, 95, 56, 10, 42, 95, 52, 65, 14, 79, 181, 238, 208, 201, 12, 246, 72, 86, 255, 172, 228, 75, 2, 17, 0, 0, 0, 4, 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