Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb3aaa5636e6345794a15a21b3a0f8e7eebabb47a44977384c6fd52a257285d6

Tx prefix hash: 5a34b520c6b39e1deb707ae6b77aeddbc1525af5efed2950897062fb045b4975
Tx public key: ed3a122638d4c0dbe589a1ddda6a936d5aa2c9373cad47bd4532904124d0d242
Timestamp: 1716350353 Timestamp [UCT]: 2024-05-22 03:59:13 Age [y:d:h:m:s]: 00:324:17:16:00
Block: 1027307 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232091 RingCT/type: yes/0
Extra: 01ed3a122638d4c0dbe589a1ddda6a936d5aa2c9373cad47bd4532904124d0d24202110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4241e0e8da7a9ed010e1e4704b85aca34a8b4b01e3fed74c9d7c9043a5780b9f 0.600000000000 1494854 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": 1027317, "vin": [ { "gen": { "height": 1027307 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4241e0e8da7a9ed010e1e4704b85aca34a8b4b01e3fed74c9d7c9043a5780b9f" } } ], "extra": [ 1, 237, 58, 18, 38, 56, 212, 192, 219, 229, 137, 161, 221, 218, 106, 147, 109, 90, 162, 201, 55, 60, 173, 71, 189, 69, 50, 144, 65, 36, 208, 210, 66, 2, 17, 0, 0, 0, 2, 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